thread VM and WASM for stack traces#299
Merged
Merged
Conversation
Collaborator
|
Hm. I'm not a huge fan of how this grows bytecode and WASM. Have you explored split debuginfo for the LLVM backend and also an equivalent for the bytecode? Either way, I think we should have a flag to exclude it from the binary and keep using that for our size measurements (maybe add new columns for the size with debuginfo). |
Contributor
|
Overall success rate on test cases: 75.6% Positive ChangesWASM Size (bytes) decreased (420 test(s))
No size growth detected. Comparison Base DetailsCompared against: Committed STATUS.md at |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.